SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Diskless node</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Diskless node</span></span>

</h1>

</header>

<p>A <b>diskless node</b> (or <b>diskless workstation</b>) is a <a href="Workstation" title="Workstation">workstation</a> or personal computer without <a href="Disk_drive" class="mw-redirect" title="Disk drive">disk drives</a>, which employs <a href="Network_booting" title="Network booting">network booting</a> to load its <a href="Operating_system" title="Operating system">operating system</a> from a <a href="Server_(computing)" title="Server (computing)">server</a>. (A computer may also be said to <i>act as a diskless node</i>, if its disks are unused and network booting is used.)

</p><p>Diskless nodes (or computers acting as such) are sometimes known as <i><a href="Network_computer" class="mw-redirect" title="Network computer">network computers</a></i> or <b>hybrid clients</b>. <i>Hybrid client</i> may either just mean diskless node, or it may be used in a more particular sense to mean a diskless node which runs <i>some</i>, but not all, <a href="Application_software" title="Application software">applications</a> remotely, as in the <a href="Thin_client" title="Thin client">thin client</a> computing architecture.

</p><p>Advantages of diskless nodes can include lower production cost, lower running costs, quieter operation, and manageability advantages (for example, centrally managed software installation).

</p><p>In many universities and in some large organizations, <a href="Personal_computer" title="Personal computer">PCs</a> are used in a similar configuration, with some or all applications stored remotely but <a href="Execution_(computers)" class="mw-redirect" title="Execution (computers)">executed</a> locally—again, for manageability reasons. However, these are not diskless nodes if they still <a href="Booting" title="Booting">boot</a> from a local <a href="Hard_drive" class="mw-redirect" title="Hard drive">hard drive</a>.

</p>

<div class="mw-heading mw-heading2"><h2 id="Distinction_between_diskless_nodes_and_centralized_computing">Distinction between diskless nodes and centralized computing</h2></div>

<p>Diskless nodes process <a href="Data_(computer_science)" title="Data (computer science)">data</a>, thus using their own <a href="Central_processing_unit" title="Central processing unit">CPU</a> and <a href="Random-access_memory" title="Random-access memory">RAM</a> to run <a href="Computer_software" class="mw-redirect" title="Computer software">software</a>, but do not store data persistently—that task is handed off to a server. This is distinct from <a href="Thin_client" title="Thin client">thin clients</a>, in which all significant processing happens remotely, on the server—the only software that runs on a thin client is the "thin" (i.e. relatively small and simple) client software, which handles simple input/output tasks to communicate with the user, such as drawing a <a href="Dialog_box" title="Dialog box">dialog box</a> on the <a href="Display_device" title="Display device">display</a> or waiting for user input.

</p><p>A collective term encompassing both thin client computing, and its technological predecessor, <a href="Computer_terminal" title="Computer terminal">text terminals</a> (which are text-only), is <a href="Centralized_computing" title="Centralized computing">centralized computing</a>. <a href="Thin_client" title="Thin client">Thin clients</a> and text terminals can both require powerful central processing facilities in the servers, in order to perform all significant processing tasks for all of the clients.

</p><p>Diskless nodes can be seen as a compromise between <a href="Rich_client" title="Rich client">rich clients</a> (such as ordinary personal computers) and centralized computing, using central storage for efficiency, but not requiring centralized processing, and making efficient use of the powerful processing power of even the slowest of contemporary CPUs, which would tend to sit idle for much of the time under the centralized computing model.

</p>

<td>

</td>

<th><a href="Centralized_computing" title="Centralized computing">Centralized computing</a> <br>or <a href="Thin_client" title="Thin client">Thin client</a>

</th>

<th>Diskless node

</th>

<th>Dataless node <sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

</th>

<th><a href="Rich_client" title="Rich client">Rich client</a>

</th></tr>

<tr>

<th>Local <a href="Hard_drive" class="mw-redirect" title="Hard drive">hard drives</a> used for data

</th>

<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No

</td>

<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No

</td>

<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No

</td>

<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes

</td></tr>

<tr>

<th>Local <a href="Hard_drive" class="mw-redirect" title="Hard drive">hard drives</a> used for OS

</th>

<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No

</td>

<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No

</td>

<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes

</td>

<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes

</td></tr>

<tr>

<th>Local general-purpose processing used

</th>

<td style="background:#FFC7C7;color:black;vertical-align:middle;text-align:center;" class="table-no">No

</td>

<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes

</td>

<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes

</td>

<td style="background:#9EFF9E;color:black;vertical-align:middle;text-align:center;" class="table-yes">Yes

</td></tr></tbody></table>

<div class="mw-heading mw-heading2"><h2 id="Principles_of_operation">Principles of operation</h2></div>

<p>The operating system (OS) for a diskless node is loaded from a server, using <a href="Network_booting" title="Network booting">network booting</a>. In some cases, removable storage may be used to initiate the bootstrap process, such as a <a href="USB_flash_drive" title="USB flash drive">USB flash drive</a>, or other bootable media such as a <a href="Floppy_disk" title="Floppy disk">floppy disk</a>, CD or DVD. However, the <a href="Firmware" title="Firmware">firmware</a> in many modern computers can be configured to locate a server and begin the bootup process automatically, without the need to insert bootable media.

</p>

<p>For network auto-booting, the <a href="Preboot_Execution_Environment" title="Preboot Execution Environment">Preboot Execution Environment</a> (PXE) or <a href="Bootstrap_Protocol" title="Bootstrap Protocol">Bootstrap Protocol</a> (BOOTP) network protocols are commonly used to find a server with files for booting the device. Standard full-size desktop PCs are able to be network-booted in this manner with an add-on network card that includes a <a href="Preboot_Execution_Environment" title="Preboot Execution Environment">Universal Network Device Interface</a> boot ROM. Diskless network booting is commonly a built-in feature of desktop and laptop PCs intended for business use, since it can be used on an otherwise disk-booted standard desktop computer to remotely run diagnostics, to install software, or to apply a <a href="Disk_image" title="Disk image">disk image</a> to the local hard drive.

</p><p>After the bootstrapping process has been initiated, as described above, bootstrapping will take place according to one of three main approaches.

</p>

<ul><li>In the first approach (used, for example, by the <a href="Linux_Terminal_Server_Project" title="Linux Terminal Server Project">Linux Terminal Server Project</a>), the <a href="Kernel_(operating_system)" title="Kernel (operating system)">kernel</a> is loaded into memory and then the rest of the operating system is accessed via a <a href="Clustered_file_system" title="Clustered file system">network filesystem</a> connection to the server. (A small <a href="RAM_drive" title="RAM drive">RAM disk</a> may be created to store temporary files locally.) This approach is sometimes called the "<a href="Network_File_System" title="Network File System">NFS</a> root" technique when used with Linux or Unix client operating systems.</li>

<li>In the second approach, the kernel of the OS is loaded, and part of the system's memory is configured as a large RAM disk, and then the remainder of the OS image is fetched and loaded into the RAM disk. This is the implementation that <a href="Microsoft" title="Microsoft">Microsoft</a> has chosen for its <a href="Windows_XP_Embedded" class="mw-redirect" title="Windows XP Embedded">Windows XP Embedded</a> remote boot feature.<sup id="cite_ref-microsoft_2-0" class="reference"><a href="#cite_note-microsoft-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup></li>

<li>In the third approach, disk operations are virtualized and are actually translated into a network protocol. The data that is usually stored in a disk drive are then stored in virtual disks files homed on a server. The disk operations such as requests to read/write disk sectors are translated into corresponding network requests and processed by a service or daemon running on the server side. This is the implementation that is used by <a href="Neoware" title="Neoware">Neoware</a> Image Manager, Ardence, VHD Central Management System<sup id="cite_ref-vhdsoft_3-0" class="reference"><a href="#cite_note-vhdsoft-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> and various "boot over iSCSI" products. This third approach differs from the first approach because what is remote is not a <a href="File_system" title="File system">file system</a> but actually a disk device (or <a href="Raw_device" title="Raw device">raw device</a>) and that the client OS is not aware that it is not running off a hard disk. This is why this approach is sometimes named "<a href="VHD_(file_format)" title="VHD (file format)">Virtual Hard Disk</a>" or "Network Virtual Disk".</li></ul>

<p>This third approach makes it easier to use client OS than having a complete disk image in RAM or using a read-only file system. In this approach, the system uses some "write cache" that stores every data that a diskless node has written. This write cache is usually a file, stored on a server (or on the client storage if any). It can also be a portion of the client RAM. This write cache can be persistent or volatile. When volatile, all the data that has been written by a specific client to the virtual disk are dismissed when said client is rebooted, and yet, user data can remain persistent if recorded in user (roaming) profiles or home folders (that are stored on remote servers). The two major commercial products (the one from <a href="Hewlett-Packard" title="Hewlett-Packard">Hewlett-Packard</a>, and the other one from <a href="Citrix_Systems" title="Citrix Systems">Citrix Systems</a>) that allow the deployment of Diskless Nodes that can boot <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a> or <a href="Linux" title="Linux">Linux</a> client OS use such write caches. The Citrix product cannot use persistent write cache, but VHD and HP product can.

</p>

</div>

<div class="mw-heading mw-heading2"><h2 id="Diskless_Windows_nodes">Diskless Windows nodes</h2></div>

<p>Windows 3.x and Windows 95 OSR1<sup id="cite_ref-microsoft2_4-0" class="reference"><a href="#cite_note-microsoft2-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> supported Remote Boot operations, from <a href="NetWare" title="NetWare">NetWare</a> servers,<sup id="cite_ref-H17007Index_5-0" class="reference"><a href="#cite_note-H17007Index-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> <a href="Microsoft_Windows" title="Microsoft Windows">Windows</a> NT Servers<sup id="cite_ref-microsoft3_6-0" class="reference"><a href="#cite_note-microsoft3-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> and even DEC <a href="Pathworks" title="Pathworks">Pathworks</a> servers.<sup id="cite_ref-microsoft4_7-0" class="reference"><a href="#cite_note-microsoft4-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup>

</p><p>Third party software vendors such as Qualystem (acquired by <a href="Neoware" title="Neoware">Neoware</a>), LanWorks (acquired by <a href="3Com" title="3Com">3Com</a>), Ardence (acquired by <a href="Citrix_Systems" title="Citrix Systems">Citrix Systems</a>), APCT<sup id="cite_ref-apct_8-0" class="reference"><a href="#cite_note-apct-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> and Xtreamining Technology<sup id="cite_ref-vhdsoft_3-1" class="reference"><a href="#cite_note-vhdsoft-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> have developed and marketed software products aimed to remote-boot newer versions of the <a href="Microsoft_Windows" title="Microsoft Windows">Windows</a> product line: Windows 95 OSR2 and Windows 98 were supported by Qualystem and Lanworks, Windows NT was supported by APCT and Ardence (called VenturCom at that time), and Windows 2000/XP/2003/Vista/Windows 7 are supported by <a href="Hewlett-Packard" title="Hewlett-Packard">Hewlett-Packard</a> (which acquired <a href="Neoware" title="Neoware">Neoware</a> which had previously acquired Qualystem) and Citrix Systems (which acquired <a href="Ardence" title="Ardence">Ardence</a>).

</p>

<div class="mw-heading mw-heading2"><h2 id="Comparison_with_rich_clients">Comparison with rich clients</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Software_installation_and_maintenance">Software installation and maintenance</h3></div>

<p>With essentially a single OS image for an array of machines (with perhaps some customizations for differences in hardware configurations among the nodes), installing software and maintaining installed software can be more efficient. Furthermore, any system changes made during operation (due to user action, worms, viruses, etc.) can be either wiped out when the power is removed (if the image is copied to a local RAM disk) such as Windows XP Embedded remote boot<sup id="cite_ref-microsoft5_9-0" class="reference"><a href="#cite_note-microsoft5-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-microsoft6_10-0" class="reference"><a href="#cite_note-microsoft6-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup> or prohibited entirely (if the image is a network filesystem). This allows use in public access areas (such as <a href="Libraries" class="mw-redirect" title="Libraries">libraries</a>) or in schools etc., where users might wish to experiment or attempt to "hack" the system.

</p><p>However, it is not necessary to implement network booting to achieve either of the above advantages - ordinary <a href="Personal_computer" title="Personal computer">PCs</a> (with the help of appropriate software) can be configured to download and reinstall their operating systems on (e.g.) a nightly basis, with extra work compared to using shared disk image that diskless nodes boot off.

</p><p>Modern diskless nodes can share the very same disk image, using a 1:N relationship (1 disk image used simultaneously by N diskless nodes). This makes it very easy to install and maintain software applications: The administrator needs to install or maintain the application only once, and the clients can get the new application as soon as they boot off the updated image. Disk image sharing is made possible because they use the write cache: No client competes for any writing in a shared disk image, because each client writes to its own cache.

</p><p>All the modern diskless nodes systems can also use a 1:1 Client-to-DiskImage relationship, where one client "owns" one disk image and writes directly into said disk image. No write cache is used then.

</p><p>Making a modification in a shared disk image is usually made this way:

</p>

<ol><li>The administrator makes a copy of the shared disk image that he/she wants to update (this can be done easily because the disk image file is opened only for reading)</li>

<li>The administrator boots a diskless node in 1:1 mode (unshared mode) from the copy of the disk image he/she just made</li>

<li>The administrator makes any modification to the disk image (for instance install a new software application, apply patches or hotfixes)</li>

<li>The administrator shutdowns the diskless node that was using the disk image in 1:1 mode</li>

<li>The administrator shares the modified disk image</li>

<li>The diskless nodes use the shared disk image (1:N) as soon as they are rebooted.</li></ol>

<div class="mw-heading mw-heading3"><h3 id="Centralized_storage">Centralized storage</h3></div>

<p>The use of central disk storage also makes more efficient use of disk storage. This can cut storage costs, freeing up capital to <a href="Investment" title="Investment">invest</a> in more reliable, modern storage technologies, such as <a href="RAID" title="RAID">RAID arrays</a> which support redundant operation, and <a href="Storage_area_network" title="Storage area network">storage area networks</a> which allow hot-adding of storage without any interruption. Further, it means that losses of disk drives to mechanical or electrical failure—which are statistically highly probable events over a timeframe of years, with a large number of disks involved—are often both less likely to happen (because there are typically fewer disk drives that can fail) and less likely to cause interruption (because they would likely be part of RAID arrays). This also means that the nodes <i>themselves</i> are less likely to have hardware failures than <a href="Rich_client" title="Rich client">rich clients</a>.

</p><p>Diskless nodes share these advantages with <a href="Thin_client" title="Thin client">thin clients</a>.

</p>

<div class="mw-heading mw-heading4"><h4 id="Performance_of_centralized_storage">Performance of centralized storage</h4></div>

<p>However, this storage efficiency can come at a price. As often happens in computing, increased storage efficiency sometimes comes at the price of decreased performance.

</p><p>Large numbers of nodes making demands on the same server simultaneously can slow down everyone's experience. However, this can be mitigated by installing large amounts of <a href="Random-access_memory" title="Random-access memory">RAM</a> on the server (which speeds up read operations by improving <a href="Cache_(computing)" title="Cache (computing)">caching</a> performance), by adding more servers (which distributes the I/O workload), or by adding more disks to a RAID array (which distributes the <i>physical</i> I/O workload). In any case this is also a problem which can affect <i>any</i> client-server network to some extent, since, of course, rich clients also use servers to store user data.

</p><p>Indeed, user data may be much more significant in size and may be accessed far more frequently than operating systems and programs in some environments, so moving to a diskless model will not <i>necessarily</i> cause a noticeable degradation in performance.

</p><p>Greater <a href="Network_bandwidth" class="mw-redirect" title="Network bandwidth">network bandwidth</a> (i.e. capacity) will also be used in a diskless model, compared to a rich client model. This does not necessarily mean that a higher capacity network infrastructure will need to be installed—it could simply mean that a higher proportion of the existing network capacity will be used.

</p><p>Finally, the combination of network data transfer <a href="Latency_(engineering)" title="Latency (engineering)">latencies</a> (physically transferring the data over the network) and contention latencies (waiting for the server to process other nodes' requests before yours) can lead to an unacceptable degradation in performance compared to using local drives, depending on the nature of the application and the capacity of the network infrastructure and the server.

</p>

<div class="mw-heading mw-heading3"><h3 id="Other_advantages">Other advantages</h3></div>

<p>Another example of a situation where a diskless node would be useful is in a possibly hazardous environment where computers are likely to be damaged or destroyed, thus making the need for inexpensive nodes, and minimal hardware a benefit. Again, thin clients can also be used here.

</p><p>Diskless machines may also consume little power and make little noise, which implies potential <a href="Environmentally_friendly" title="Environmentally friendly">environmental benefits</a> and makes them ideal for some <a href="Computer_cluster" title="Computer cluster">computer cluster</a> applications.

</p>

<div class="mw-heading mw-heading2"><h2 id="Comparison_with_thin_clients">Comparison with thin clients</h2></div>

<p>Both thin client and diskless node architectures employ diskless clients which have advantages over rich clients (see above), but differ with regard to the location of processing.

</p>

<div class="mw-heading mw-heading3"><h3 id="Advantages_of_diskless_nodes_over_thin_clients">Advantages of diskless nodes over thin clients</h3></div>

<ul><li><b>Distributed load</b> The <i>processing</i> load of diskless nodes is distributed. Each user gets its own processing isolated environment, barely affecting other users in the network, as long as their workload is not filesystem-intensive. Thin clients rely on the central server for the processing and thus require a fast server. When the central server is busy and slow, both kinds of clients will be affected, but thin clients will be slowed completely, whereas diskless nodes will only be slowed when accessing data on the server.</li>

<li><b>Better multimedia performance</b>. Diskless nodes have advantages over thin clients in <a href="Multimedia" title="Multimedia">multimedia</a>-rich applications that would be bandwidth intensive if fully served. For example, diskless nodes are well suited for <a href="Video_gaming" class="mw-redirect" title="Video gaming">video gaming</a> because the rendering is local, lowering the latency.</li>

<li><b>Peripheral support</b> Diskless nodes are typically ordinary personal computers or <a href="Workstation" title="Workstation">workstations</a> with no hard drives supplied, which means the usual large variety of <a href="Peripheral" title="Peripheral">peripherals</a> can be added. By contrast, thin clients are typically very small, sealed boxes with no possibility for internal expansion, and limited or non-existent possibility for external expansion. Even if e.g. a <a href="USB" title="USB">USB</a> device can be <i>physically</i> attached to a thin client, the thin client software might not support peripherals beyond the basic input and output devices - for example, it may not be compatible with <a href="Graphics_tablet" title="Graphics tablet">graphics tablets</a>, <a href="Digital_camera" title="Digital camera">digital cameras</a> or <a href="Image_scanner" title="Image scanner">scanners</a>.</li></ul>

<div class="mw-heading mw-heading3"><h3 id="Advantages_of_thin_clients_over_diskless_nodes">Advantages of thin clients over diskless nodes</h3></div>

<ul><li>The <b>hardware is cheaper</b> on thin clients, since processing requirements on the client are minimal, and <a href="3D_acceleration" class="mw-redirect" title="3D acceleration">3D acceleration</a> and elaborate audio support are not usually provided. Of course, a diskless node can also be purchased with a cheap CPU and minimal multimedia support, if suitable. Thus, cost savings may be smaller than they first appear for some organizations. However, many large organizations habitually buy hardware with a higher than necessary specification to meet the needs of particular applications and uses, or to ensure <a href="Future_proofing" class="mw-redirect" title="Future proofing">future proofing</a> <i>(see next point)</i>. There are also less "rational" reasons for overspecifying hardware which quite often come into play: departments wastefully using up budgets in order to retain their current budget levels for next year; and uncertainty about the future, or lack of technical knowledge, or lack of care and attention, when choosing PC specifications. Taking all these factors into account, thin clients may bring the most substantial savings, as only the servers are likely to be substantially "gold-plated" and/or "future-proofed" in the thin client model.</li>

<li><b>Future proofing</b> is not much of an issue for thin clients, which are likely to remain useful for the entirety of their replacement cycle - one to four years, or even longer - as the burden is on the servers. There are issues when it comes to diskless nodes, as the processing load is potentially much higher, thus meaning more consideration is required when purchasing. Thin client networks may require significantly more powerful servers in the future, whereas a diskless nodes network may in future need a server upgrade, a client upgrade, or both.</li>

<li>Thin client networks have <b>less network bandwidth consumption</b> potentially, since much data is simply read by the server and processed there, and only transferred to the client in small pieces, as and when needed for display. Also, transferring graphical data to the display is usually more suited for efficient <a href="Data_compression" title="Data compression">data compression</a> and optimisation technologies (see e.g. <a href="NX_technology" title="NX technology">NX technology</a>) than transferring arbitrary <a href="Computer_program" title="Computer program">programs</a>, or user data. In many typical application scenarios, both total bandwidth consumption and "burst" consumption would be expected to be less for an efficient thin client, than for a diskless node.</li></ul>

<ul><li><a href="Thin_client" title="Thin client">Thin client</a></li>

<li><a href="Network_block_device" title="Network block device">Network block device</a></li>

<li><a href="Diskless_Remote_Boot_in_Linux" title="Diskless Remote Boot in Linux">Diskless Remote Boot in Linux</a></li>

<li><a href="Preboot_Execution_Environment" title="Preboot Execution Environment">Preboot Execution Environment</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="Notes">Notes</h2></div>

<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text">page 166, Managing NFS and NIS, By Mike Eisler, Ricardo Labiaga, Hal Stern, O'Reilly Media, Inc., Jul 1, 2001</span>

</li>

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20080423084418/http://msdn2.microsoft.com/en-us/embedded/aa731381.aspx">"Remote Boot Feature Overview"</a>. <i>Windows Embedded Developer Center</i>. Archived from <a rel="nofollow" class="external text" href="http://msdn2.microsoft.com/en-us/embedded/aa731381.aspx">the original</a> on 2008-04-23.</cite></span>

</li>

<li id="cite_note-vhdsoft-3"><span class="mw-cite-backlink">^ <a href="#cite_ref-vhdsoft_3-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-vhdsoft_3-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20140323032852/http://www.vhdsoft.com/index.php?menu_id=0&submenu_id=0">"VHD Central Management System"</a>. <i>Xtreaming Technology Inc</i>. Archived from <a rel="nofollow" class="external text" href="http://www.vhdsoft.com/index.php?menu_id=0&submenu_id=0">the original</a> on 2014-03-23<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-03-22</span></span>.</cite></span>

</li>

<li id="cite_note-microsoft2-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-microsoft2_4-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20061124173505fw_/http://www.microsoft.com/technet/archive/win95/rk04_svr.mspx">"Windows 95: Server-Based Setup for Windows 95"</a>. <i><a href="Microsoft_TechNet" title="Microsoft TechNet">Microsoft TechNet</a></i>. Archived from <a rel="nofollow" class="external text" href="http://www.microsoft.com/technet/archive/win95/rk04_svr.mspx">the original</a> on 2006-11-24.</cite></span>

</li>

<li id="cite_note-H17007Index-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-H17007Index_5-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20140322120942/http://h17007.www1.hp.com/us/en/networking/index.aspx#.Uy19mS-l1c8">"HP Networking: switches, routers, wired, wireless, HP TippingPoint Security – HP®"</a>. h17007.www1.hp.com. Archived from <a rel="nofollow" class="external text" href="http://h17007.www1.hp.com/us/en/networking/index.aspx#.Uy33Sn18hpg">the original</a> on 22 March 2014<span class="reference-accessdate">. Retrieved <span class="nowrap">22 March</span> 2014</span>.</cite></span>

</li>

<li id="cite_note-microsoft3-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-microsoft3_6-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20140323014635/http://support.microsoft.com/kb/158278">"Explanation of How Windows NT Server 4.0 Remoteboot Works"</a>. support.microsoft.com. Archived from <a rel="nofollow" class="external text" href="http://support.microsoft.com/kb/158278">the original</a> on 2014-03-23<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-03-22</span></span>.</cite></span>

</li>

<li id="cite_note-microsoft4-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-microsoft4_7-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20140323002413/http://support.microsoft.com/kb/82654">"DEC Pathworks Remote Boot Workstations Under Windows 3.1"</a>. support.microsoft.com. Archived from <a rel="nofollow" class="external text" href="http://support.microsoft.com/kb/82654">the original</a> on 2014-03-23<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-03-22</span></span>.</cite></span>

</li>

<li id="cite_note-apct-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-apct_8-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20010222055859/http://www.apct.net/en/pd_absolutboot.html">"AbsolutBoot"</a>. <i>APCT - Advanced PC Technologies</i>. Archived from <a rel="nofollow" class="external text" href="http://www.apct.net/en/pd_absolutboot.html">the original</a> on 2001-02-22.</cite></span>

</li>

<li id="cite_note-microsoft5-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-microsoft5_9-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFChamberlain2004" class="citation web cs1">Chamberlain, Mark (February 2004). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20120515201115/http://msdn.microsoft.com/en-us/library/ms838569.aspx">"Deploying Windows XP Embedded Remote Boot"</a>. <i><a href="Microsoft_Developer_Network" title="Microsoft Developer Network">Microsoft Developer Network</a></i>. Archived from <a rel="nofollow" class="external text" href="http://msdn.microsoft.com/en-us/library/ms838569.aspx">the original</a> on 2012-05-15.</cite></span>

</li>

<li id="cite_note-microsoft6-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-microsoft6_10-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFSyed2002" class="citation web cs1">Syed, Saad (November 2002). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20121013174724/http://msdn.microsoft.com/en-us/library/ms838543.aspx">"RAM Boot Using SDI in Windows XP Embedded with Service Pack 1"</a>. <i><a href="Microsoft_Developer_Network" title="Microsoft Developer Network">Microsoft Developer Network</a></i>. Archived from <a rel="nofollow" class="external text" href="http://msdn.microsoft.com/en-us/library/ms838543.aspx">the original</a> on 2012-10-13.</cite></span>

</li>

</ol></div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

<ul><li><cite id="CITEREFMaroney1987" class="citation journal cs1">Maroney, Tim (1987). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20060428144123/http://www.mactech.com/articles/mactech/Vol.03/03.04/File,DiskServers/">"File Servers versus Disk Servers"</a>. <i><a href="MacTech" title="MacTech">MacTech</a></i>. <b>3</b> (4). Archived from <a rel="nofollow" class="external text" href="http://www.mactech.com/articles/mactech/Vol.03/03.04/File,DiskServers">the original</a> on 2006-04-28<span class="reference-accessdate">. Retrieved <span class="nowrap">2007-07-23</span></span>.</cite></li>

<li><cite id="CITEREFKari1989" class="citation thesis cs1">Kari, Hannu H. (1989). <i>Diskless Workstations in a Local Area Network</i> (License of Science in Technology). <a href="Helsinki_University_of_Technology" title="Helsinki University of Technology">Helsinki University of Technology</a>, department of Electrical Engineering.</cite></li>

<li><cite id="CITEREFFosterHughes1991" class="citation conference cs1">Foster, Louis A.; Hughes, Norman L. (March 1991). <a rel="nofollow" class="external text" href="http://portal.acm.org/ft_gateway.cfm?id=107039&type=pdf">"Making Files Real With a Virtual Disk"</a> <span class="cs1-format">(PDF)</span>. <i>Proceedings of the twenty-second SIGCSE technical symposium on Computer science education - SIGCSE '91</i>. Twenty-second SIGCSE technical symposium on Computer science education. pp. <span class="nowrap">199–</span>204. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F107004.107039">10.1145/107004.107039</a></span>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0897913779</bdi>.</cite></li>

/* start https://en.wikipedia.org/ */

.mw-parser-output .citation{word-wrap:break-word}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}

/* end https://en.wikipedia.org/ */

</style><span class="citation patent" id="CITEREFFlahertyAbrahams1992"><a rel="nofollow" class="external text" href="https://worldwide.espacenet.com/textdoc?DB=EPODOC&IDX=US5146568">US 5146568</a>, Flaherty, James E. & Abrahams, Alan, "Remote bootstrapping a node over communication link by initially requesting remote storage access program which emulates local disk to load other programs", published 1992-09-08, assigned to <a href="Digital_Equipment_Corporation" title="Digital Equipment Corporation">Digital Equipment Corporation</a></span><span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Apatent&rft.number=5146568&rft.cc=US&rft.title=Remote+bootstrapping+a+node+over+communication+link+by+initially+requesting+remote+storage+access+program+which+emulates+local+disk+to+load+other+programs&rft.inventor=Flaherty&rft.assignee=%5B%5BDigital+Equipment+Corporation%5D%5D&rft.pubdate=1992-09-08"><span style="display: none;"> </span></span></li>

<li><cite id="CITEREFHayter1993" class="citation report cs1">Hayter, Mark David (November 1993). <a rel="nofollow" class="external text" href="http://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-319.html">A Workstation Architecture to Support Multimedia</a> (Report). Computer Laboratory, University of Cambridge. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.48456%2Ftr-319">10.48456/tr-319</a>. UCAM-CL-TR-319.</cite></li>

<li><span class="citation patent" id="CITEREFAbdousDemortainDalongvile1996"><a rel="nofollow" class="external text" href="https://worldwide.espacenet.com/textdoc?DB=EPODOC&IDX=US5577210">US 5577210</a>, Abdous, Arave; Demortain, Stephane & Dalongvile, Didier, "Remote booting of an operating system by a network", published 1996-11-19, assigned to <a href="Groupe_Bull" title="Groupe Bull">Bull S.A.</a></span><span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Apatent&rft.number=5577210&rft.cc=US&rft.title=Remote+booting+of+an+operating+system+by+a+network&rft.inventor=Abdous&rft.assignee=%5B%5BGroupe_Bull%7CBull+S.A.%5D%5D&rft.pubdate=1996-11-19"><span style="display: none;"> </span></span></li>

<li><cite id="CITEREFLeeThekkath,_Chandramohan_A.1996" class="citation conference cs1">Lee, Edward K.; Thekkath, Chandramohan A. (1996). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110401012138/http://thekkath.org/Documents/petal.pdf"><i>Petal: Distributed Virtual Disks</i></a> <span class="cs1-format">(PDF)</span>. 7th International Conference on Architectural Support for Programming Languages and Operating Systems. Archived from <a rel="nofollow" class="external text" href="http://thekkath.org/Documents/petal.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2011-04-01<span class="reference-accessdate">. Retrieved <span class="nowrap">2009-07-21</span></span>.</cite></li>

<li><cite id="CITEREFLeslieMcAuley1996" class="citation report cs1">Leslie, Ian; <a href="Derek_McAuley" title="Derek McAuley">McAuley, Derek</a> (July 24, 1996). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20031021062607/http://www.cl.cam.ac.uk/Research/SRG/netos/plana/danos/final_report.ps">Operating systems support for the Desk Area Network</a> (Report). Archived from <a rel="nofollow" class="external text" href="http://www.cl.cam.ac.uk/Research/SRG/netos/plana/danos/final_report.ps">the original</a> <span class="cs1-format">(Postscript)</span> on 2003-10-21.</cite></li>

<li><cite class="citation pressrelease cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20100210173338/http://pressreleasespider.com/feed2885.aspx">"Management of Diskless Windows 2000 and XP Stations from a Linux Server"</a> (Press release). 2004. Archived from <a rel="nofollow" class="external text" href="http://pressreleasespider.com/feed2885.aspx">the original</a> on 2010-02-10.</cite></li></ul>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li>Network Block Device home page <a rel="nofollow" class="external free" href="https://nbd.sourceforge.net/">https://nbd.sourceforge.net/</a></li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Computer_sizes_and_classes279" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Computer_sizes_and_classes279" style="font-size:114%;margin:0 4em"><a href="List_of_computer_size_categories" title="List of computer size categories">Computer sizes</a> and <a href="Classes_of_computers" title="Classes of computers">classes</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Microcomputer" title="Microcomputer">Micro</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Static</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Computer_appliance" title="Computer appliance">Appliances</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Arcade_cabinet" title="Arcade cabinet">Arcade cabinet</a></li>

<li><a href="Internet_appliance" title="Internet appliance">Internet appliance</a></li>

<li><a href="Intelligent_terminal" class="mw-redirect" title="Intelligent terminal">Intelligent terminal</a></li>

<li><a href="Interactive_kiosk" title="Interactive kiosk">Interactive kiosk</a></li>

<li><a href="Rich_client" title="Rich client">Rich client</a></li>

<li><a href="Simulator_ride" title="Simulator ride">Simulator</a></li>

<li><a href="Smart_speaker" title="Smart speaker">Smart speaker</a></li>

<li><a href="Smart_TV" title="Smart TV">Smart TV</a></li>

<li><a href="Thin_client" title="Thin client">Thin client</a></li>

<li><a href="Video_game_console" title="Video game console">Video game console</a>

<ul><li><a href="Home_video_game_console" title="Home video game console">Home console</a></li>

<li><a href="Microconsole" title="Microconsole">Microconsole</a></li></ul></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Computers</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">By use</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Gaming_computer" title="Gaming computer">Gaming</a></li>

<li><a href="Industrial_PC" title="Industrial PC">Industrial</a></li>

<li><a href="Personal_computer" title="Personal computer">Personal</a>

<ul><li><a href="Personal_supercomputer" title="Personal supercomputer">Personal super</a></li></ul></li>

<li><a href="Public_computer" title="Public computer">Public</a></li>

<li><a href="Server_(computing)" title="Server (computing)">Server</a>

<ul><li><a href="Home_server" title="Home server">Home server</a></li></ul></li>

<li><a href="Workstation" title="Workstation">Workstation</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">By size</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Panel_PC" title="Panel PC">Panel</a></li>

<li><a href="Table_computer" title="Table computer">Tabletop</a></li>

<li><a href="Surface_computer" title="Surface computer">Surface</a></li></ul></li>

<li><a href="Desktop_computer" title="Desktop computer">Desktop</a>

<ul><li><a href="Deskside_computer" class="mw-redirect" title="Deskside computer">Deskside</a></li>

<li><a href="Pizza-box_form_factor" title="Pizza-box form factor">Pizza box</a></li>

<li><a href="Computer_tower" title="Computer tower">Tower</a></li></ul></li>

<li><a href="Portable_computer" title="Portable computer">Portable</a></li>

<li><a href="Small_form_factor_PC" title="Small form factor PC">Small form factor</a>

<li><a href="Stick_PC" title="Stick PC">Stick PC</a></li></ul></li>

<ul><li><a href="Blade_server" title="Blade server">Blade server</a></li>

<li><a href="Blade_PC" title="Blade PC">Blade PC</a></li></ul></li></ul>

</div></td></tr></tbody></table><div></div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Mobile_computing" title="Mobile computing">Mobile</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Laptop" title="Laptop">Laptop</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="2-in-1_laptop#2-in-1_convertible" title="2-in-1 laptop">Convertible</a></li></ul></li>

<li><a href="Cloudbook" title="Cloudbook">Cloudbook</a></li>

<li><a href="Mobile_workstation" title="Mobile workstation">Mobile workstation</a></li>

<li><a href="Notebook_computer" title="Notebook computer">Notebook</a></li>

<li><a href="Subnotebook" title="Subnotebook">Subnotebook</a>

<ul><li><a href="Netbook" title="Netbook">Netbook</a></li>

<li><a href="Smartbook" title="Smartbook">Smartbook</a></li></ul></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Tablet_computer" title="Tablet computer">Tablet</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="2-in-1_laptop#2-in-1_detachable" title="2-in-1 laptop">Detachable</a></li>

<li><a href="Phablet" title="Phablet">Phablet</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Mobile_device" title="Mobile device">Handheld</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Electronic_organizer" title="Electronic organizer">Electronic organizer</a></li>

<li><a href="E-reader" title="E-reader">E-reader</a></li>

<li><a href="Handheld_game_console" title="Handheld game console">Handheld game console</a></li>

<li><a href="Handheld_PC" title="Handheld PC">Handheld PC</a></li>

<li><a href="Mobile_data_terminal" title="Mobile data terminal">Mobile data terminal</a></li>

<li><a href="Mobile_phone" title="Mobile phone">Mobile phone</a>

<ul><li><a href="Camera_phone" title="Camera phone">Camera</a></li>

<li><a href="Feature_phone" title="Feature phone">Feature</a></li>

<li><a href="Smartphone" title="Smartphone">Smartphone</a>

<ul><li><a href="Foldable_smartphone" title="Foldable smartphone">Foldable</a></li></ul></li></ul></li>

<li><a href="Palmtop_PC" title="Palmtop PC">Palmtop PC</a></li>

<li><a href="Personal_digital_assistant" title="Personal digital assistant">Personal digital assistant</a></li>

<li><a href="Pocket_computer" title="Pocket computer">Pocket</a></li>

<li><a href="Portable_data_terminal" title="Portable data terminal">Portable data terminal</a></li>

<li><a href="Portable_media_player" title="Portable media player">Portable media player</a></li>

<li><a href="Siftable" title="Siftable">Siftable</a></li>

<li><a href="Ultra-mobile_PC" title="Ultra-mobile PC">Ultra-mobile PC</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Calculator" title="Calculator">Calculator</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Graphing_calculator" title="Graphing calculator">Graphing</a></li>

<li><a href="Programmable_calculator" title="Programmable calculator">Programmable</a></li>

<li><a href="Scientific_calculator" title="Scientific calculator">Scientific</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Wearable_computer" title="Wearable computer">Wearable</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Fitness_tracker" title="Fitness tracker">Fitness tracker</a>

<ul><li><a href="Smart_band" class="mw-redirect" title="Smart band">Smart band</a></li></ul></li>

<li><a href="Watch#Digital" title="Watch">Digital wristwatch</a>

<ul><li><a href="Calculator_watch" title="Calculator watch">Calculator watch</a></li>

<li><a href="Smartwatch" title="Smartwatch">Smartwatch</a></li>

<li><a href="GPS_watch" title="GPS watch">Sportwatch</a></li></ul></li>

<li><a href="Smartglasses" title="Smartglasses">Smartglasses</a></li>

<li><a href="Smart_ring" title="Smart ring">Smart ring</a></li></ul>

<li><a href="Superminicomputer" title="Superminicomputer">Supermini</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Large</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Mainframe_computer" title="Mainframe computer">Mainframe</a></li>

<li><a href="Minisupercomputer" title="Minisupercomputer">Minisuper</a></li>

<li><a href="Supercomputer" title="Supercomputer">Super</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Others</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Embedded_system" title="Embedded system">Embedded system</a></li>

<li><a href="Information_appliance" title="Information appliance">Information appliance</a></li>

<li><a href="Microcontroller" title="Microcontroller">Microcontroller</a></li>

<li><a href="Rugged_computer" title="Rugged computer">Rugged</a>

<ul><li><a href="Rugged_smartphone" title="Rugged smartphone">Rugged smartphone</a></li></ul></li>

<li><a href="Single-board_computer" title="Single-board computer">Single-board</a>

<ul><li><a href="Computer-on-module" title="Computer-on-module">Computer-on-module</a></li></ul></li>

<li><a href="Smartdust" title="Smartdust">Smartdust</a></li>

<li><a href="Wireless_sensor_network" title="Wireless sensor network">Wireless sensor network</a></li></ul>

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2"><div>

<ul><li><span class="noviewer" typeof="mw:File"><span title="Category"></span></span> Category</li></ul>

</div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-05-26" href="https://en.wikipedia.org/wiki/?title=Diskless_node&oldid=1292296724">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>